SUPPORT / SAMPLES & SAS NOTES
 

Support

Installation Note 56231: Failures occur during configuration of the SAS® Detail Data Store for Banking 4.9 hot fix

DetailsHotfixAboutRate It

When you apply hot fixes to SAS Detail Data Store for Banking 4.9, failures might occur under the following conditions.

Errors You Might See in the SAS Log under These Conditions

The included hotfix file bdds_datachg_library_parms.sas could not be found.
If the downloaded scripts provided with the hot fix are not in the file path parameter passed to the overall script, the process fails.
ERROR: Library_parms did not execute correctly. Correct and rerun.
After executing the bdds_datachg_library_parms.sas script, the libref did not come through correctly. This issue can occur if there are multiple librefs by the same name (DDS) or no DDS libref was found. Or, alternatively, if the path, engine, schema, or authdomain are not set correctly. The LIBNAME statement is built from the SAS metadata on the library. Make the correction to that SAS metadata and rerun this hot fix.
ERROR: Library_parms did not execute correctly. Correct and rerun.

When the script checks the SAS metadata, if duplicates are found, then this message is displayed and the process stops.

ERROR: Duplicate DDS libraries found in SAS metadata. Please check only one library and no other dds libraries are assigned.

If the DDS libref in SAS metadata is not for a SAS or Oracle library, then the following message is produced.

ERROR: Library requires SAS or Oracle DDS libref.

When the script checks whether the library exists, the code allocates the library based on the SAS metadata properties. If the library does not allocate, then this message is received.

ERROR: dds Library does not exist. Process ending.

The hot fix primary script, bdds_datachg_overall_script.sas, includes a passed-in parameter for the path where the scripts are downloaded. If the execution script does not exist in that path, then an error like the following is generated, where xyz represents the path. In this case, you need to correct the path in the script macro call section and rerun.

ERROR: Script files are not available in the provided path xyz. Please review and correct.

What To Do

If you encounter any of these situations during any application of SAS Detail Data Store for Banking 4.9 hot fixes, correct the libref problem by removing the multiple librefs or by ensuring that your DDS libref is named DDS. Then follow the steps below to fix the errors and complete hot fix deployment.

  1. Start SAS using the SAS Config SASApp .bat or .sh file, logging in as the data administrator.
    The user ID must have access to the SAS metadata for SAS Detail Data Store for Banking 4.9. By using the data administrator login, the scripts execute with no prompting for user ID and password because it uses the authdomain for authentication. You can run the script in the SAS Program Editor using Base SAS® with the metadata server (see examples below), SAS® Enterprise Guide®, or the code section in SAS® Data Integration Studio.

    • In a Windows operating environment: SASConfig\sever-content-name\sas.bat
      For example: C:\SAS\Config\Lev1\SASApp\sas.bat

    • In a UNIX operating environment: SASConfig/sever-content-name/sas.sh
      For example: /SAS//Lev1/SASApp/sas.sh
  2. Copy the \upgrade\ddl\bdds_datachg_overall_script.sas into your SAS session. The path where your hot fix scripts were installed should be identified in the t_fileloc= in the macro call. If this path is incorrect or missing, it must to be corrected or added as needed. Then execute, review log, and confirm success.


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Detail Data Store for BankingMicrosoft® Windows® for x644.95.19.4 TS1M39.4 TS1M3
Microsoft Windows 8 Enterprise 32-bit4.95.19.4 TS1M39.4 TS1M3
Microsoft Windows 8 Enterprise x644.95.19.4 TS1M39.4 TS1M3
Microsoft Windows 8 Pro 32-bit4.95.19.4 TS1M39.4 TS1M3
Microsoft Windows 8 Pro x644.95.19.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Enterprise 32-bit4.95.19.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Enterprise x644.95.19.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Pro4.95.19.4 TS1M39.4 TS1M3
Microsoft Windows 8.1 Pro 32-bit4.95.19.4 TS1M39.4 TS1M3
Microsoft Windows Server 20084.95.19.4 TS1M39.4 TS1M3
Microsoft Windows Server 2008 R24.95.19.4 TS1M39.4 TS1M3
Microsoft Windows Server 2008 for x644.95.19.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 Datacenter4.95.19.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 R2 Datacenter4.95.19.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 R2 Std4.95.19.4 TS1M39.4 TS1M3
Microsoft Windows Server 2012 Std4.95.19.4 TS1M39.4 TS1M3
Windows 7 Enterprise 32 bit4.95.19.4 TS1M39.4 TS1M3
Windows 7 Enterprise x644.95.19.4 TS1M39.4 TS1M3
Windows 7 Home Premium 32 bit4.95.19.4 TS1M39.4 TS1M3
Windows 7 Home Premium x644.95.19.4 TS1M39.4 TS1M3
Windows 7 Professional 32 bit4.95.19.4 TS1M39.4 TS1M3
Windows 7 Professional x644.95.19.4 TS1M39.4 TS1M3
Windows 7 Ultimate 32 bit4.95.19.4 TS1M39.4 TS1M3
Windows 7 Ultimate x644.95.19.4 TS1M39.4 TS1M3
64-bit Enabled AIX4.95.19.4 TS1M39.4 TS1M3
64-bit Enabled Solaris4.95.19.4 TS1M39.4 TS1M3
HP-UX IPF4.95.19.4 TS1M39.4 TS1M3
Linux for x644.95.19.4 TS1M39.4 TS1M3
Solaris for x644.95.19.4 TS1M39.4 TS1M3
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.